Methods and Systems for Electronic Data Exchange Utilizing Centralized Management Technology

ABSTRACT

Methods and systems are provided for exchanging information between companies in a partnership. One method embodiment includes operatively associating a first company with a transaction directory through a directory management portal. The transaction directory is configured to permit establishment of at least one connection to a translation engine for permitting at least one transaction to occur through the connection. The method also includes connecting at least a second company to the translation engine to permit the transaction to occur between at least the first and second companies. The transaction includes an exchange of information between at least the first and second companies.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of co-pending U.S. patent application Ser. No. 10/293,247, entitled “Methods and Systems for Electronic Data Exchange Utilizing Centralized Management Technology” filed Nov. 12, 2002, which is a continuation of U.S. patent application Ser. No. 10/087,733, now abandoned, entitled “Methods and Systems for Electronic Data Exchange Utilizing Centralized Management Technology” filed Mar. 4, 2002, which claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 60/273,088 filed Mar. 2, 2001, each of which is incorporated herein by reference in its entirety.

BACKGROUND

To compete more effectively in the marketplace, an increasing number of commercial entities have decided to engage in strategic business alliances or partnerships. Strategic alliances permit companies to accelerate revenue growth and market expansion by providing access to investment capital, technology, markets, resources and different skill sets. The benefits offered by an alliance or partnership arrangement can enhance the ability of a company to produce and deliver products and services in a competitive marketplace. Competition is particularly an issue for relatively smaller companies that may not have the financial resources, information technology, and market access of larger commercial enterprises.

A strategic alliance usually requires the companies involved to share a variety of information. One solution for information exchange is installation of a frame relay to connect companies and establish a medium for data transactions. The static nature of frame relay technology, however, limits flexibility of the business decisions that can be made by the companies. As more connection options have become available, businesses have been able to choose a connectivity mix based on two primary business drivers: the company's pricing model and its partnering strategies. Connectivity options such as the Internet and other networking arrangements including, for example, secure hosting and IP-based VPN, have become available to entities seeking to leverage strategic business alliances. In addition, many companies have migrated to high-speed dynamic solutions. The use of dynamic extranets, for example, is expected to continue to grow in association with facilitation of information exchange between and among companies in strategic alliances.

It can be appreciated that companies that participate in strategic alliances must address a number of challenges. Once connected, a company in the alliance must identify and allocate resources to create point-to-point application integration with one or more of their alliance partners. Furthermore, business leaders often pursue connectivity decisions that lock the company into a long-term partnership or force the company into a bidding marketplace: there is often no middle ground between these extremes.

Companies that choose to grow through strategic partnerships may be forced to compromise information technology and systems security. Every connection that a company creates typically requires providing access through one or more firewalls of its computer systems. The purpose of a firewall is to limit external access to the computer systems and proprietary information of a company. This purpose can be frustrated, though, by the efforts of the company to improve connectivity and promote data exchange with its strategic partners.

In addition, establishing industry or cross-industry standards can be difficult or impossible, because conventional computing models are usually developed as single-company solutions and technology is rapidly changing. As a result, financial resources must be expended to conduct application integration projects with partners. Effective connectivity may require, for example, a common software application installed by all partners in an alliance to permit data exchange and collaboration. Therefore, some partners may be forced into using an undesirable software application, and new partners who may be added to the alliance may be forced to install and use the same software application to permit information exchange within the alliance.

To maintain competitiveness in the marketplace, companies must expend resources to perform research and development and/or to acquire new technology for producing and providing products and services. The ability of a company to increase the pace of its product development cycle and decrease the time to market for new products and services has a direct impact on the commercial success of the company. To focus on core competencies and conserve time, companies need to pursue collaborative efforts to expand their technical and operational resources pursuant to new product development. These collaborative efforts often involve cross-enterprise collaboration that requires effective information exchange.

Many companies experience delays in new product development due to a number of factors including, for example, isolated upfront planning, execution of project tasks in a linear, non-parallel fashion, misalignment of expectations between partners, poor or ineffective means of communication, and incompatible corporate cultures. An overarching problem is that the middle market cannot usually afford the sorts of tools that are necessary to allow collaboration between companies. Conventional ways of exchanging information in a collaborative effort between companies include electronic mail, exchange of electronic documents, video conferencing, telephone communication, and the like. These conventional ways of exchanging information are often ineffective at maximizing collaborative efforts.

What are needed, therefore, are improved methods and systems for centralized management of electronic data exchange between and among partners involved in a strategic alliance or partnership.

SUMMARY

In one embodiment of the present methods and systems, a method is provided for exchanging information between companies in a partnership. The method includes operatively associating a first company with a transaction directory through a directory management portal. The transaction directory is configured to permit establishment of at least one connection to a translation engine for permitting at least one transaction to occur through the connection. The method also includes connecting at least a second company to the translation engine to permit the transaction to occur between at least the first and second companies. The transaction includes an exchange of information between at least the first and second companies. In certain aspects of the present methods, the directory management portal and/or the transaction directory are managed by a centralized manager. In other aspects of the present methods, the translation engine operates externally with respect to at least one software application employed by the companies. Computer-readable media embodiments of the present methods are also provided.

In another embodiment of the present methods and systems, a system is provided for exchanging information between companies in a partnership. The system includes a directory management portal operatively associate with a first company and a transaction directory configured to be accessible by the company through the directory management portal. The transaction directory is configurable to establish at least one connection for the company. The system also includes a translation engine operatively associated with the transaction directory to permit at least one transaction to occur through the connection. The transaction includes information exchangeable between the first company and at least a second company.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic diagram of a conventional embodiment of a system for providing information exchange between partner entities;

FIG. 1B is a schematic diagram of a conventional embodiment of a system for providing information exchange between partner entities;

FIG. 2 is a schematic diagram of one embodiment of a system for facilitating information exchange between partner entities;

FIG. 3 is a process flow diagram of one embodiment of a method for facilitating information exchange between partner companies;

FIG. 4 is a schematic diagram of one embodiment of a system for facilitating information exchange between partner companies in association with product design and development;

FIG. 5 is an illustration showing sample details of various aspects of certain elements of FIG. 4;

FIG. 6 is a table of terminology applied to certain embodiments of the present methods and systems;

FIG. 7 is a schematic diagram illustrating one embodiment of a centralized manager and its associated functionality that can be employed to perform information exchange;

FIG. 8 is a schematic diagram illustrating one embodiment of the interaction of a centralized manager and multiple electronic business centers;

FIG. 9 is a table illustrating various embodiments of potential tools that can be applied to certain embodiments of the present methods and systems;

FIG. 10 is a table illustrating various embodiments of potential tools that can be applied to certain embodiments of the present methods and systems;

FIG. 11 is a table illustrating various embodiments of potential tools that can be applied to certain embodiments of the present methods arid systems;

FIG. 12 is a table illustrating various embodiments of potential tools that can be applied to certain embodiments of the present methods and systems;

FIG. 13 is a table illustrating various embodiments of potential tools that can be applied to certain embodiments of the present methods and systems;

FIG. 14 is a table illustrating various embodiments of potential tools that can be applied to certain embodiments of the present methods and systems; and,

FIG. 15 is a table illustrating various embodiments of potential tools that can be applied to certain embodiments of the present methods and systems.

DETAILED DESCRIPTION

As sometimes used herein, the term “CONDOR” generally refers to methods and systems for electronic data exchange that are associated with methods and systems for managing data transactions between and among commercial entities such as, for example, companies or organizations involved in a strategic partnership or alliance.

As sometimes used herein, the term “HALO” generally refers to methods and systems for electronic data exchange that are associated with centralization of functions including, for example, product/service design and prototyping, product planning, partnering activities for research and development, and the like.

Referring now to FIGS. 1A and 1B, in an illustration of conventional connectivity methods and systems, Company A (2) agrees to share data with Company B (4) through a connection for a transaction 6. It can be appreciated that the transaction 6 involves an exchange of information such as the exchange of data 8 developed in one or more software applications 10 of Company A (2) with data 12 developed in one or more software applications 14 of Company B (4). In effecting the transaction 6 of information, Company A (2) and Company 8 (4) collaborate to develop compatible data formats and network configurations that promote effective transmission of data through the transaction 6.

In operation, Company A (2) implements custom integration software code 16 to format its data 8 for transmission through the transaction 6 to Company B (4). Company A (2) also configures its network firewalls 18 to allow an external connection and the transaction 6 with Company B (4). Company B (4) also implements integration software code 20 to receive and format data transmitted by Company A (2) through the transaction 6. It can be appreciated that at least one software application included in applications 10, 14 needs to be common between Company A (2) and Company B (4) to permit an exchange of information.

In an effort similar to Company A (2), Company B (4) configures its network firewalls 22 to create an external connection with Company A (2). This external connection permits the transaction 6 to exchange information between Company A (2) and Company B (4). Once the appropriate connections and integration software modifications are implemented, the data 12 of Company B (4) can also be transmitted through the transaction 6 to Company A (2).

As can be seen in FIG. 1B, a system of multiple point-to-point connections can be created with the addition of Company C (24), for example, as a partner in the strategic alliance between Company A (2) and Company 8 (4). As shown, the exchange of information becomes more complex as the number of partners 2, 4, 24 and connections for transactions (e.g., 6A and 68) increases. Furthermore, it can be appreciated that it may be difficult to disconnect, connect, and/or reconnect partners in such an information sharing arrangement in an effective and convenient manner.

Referring now to FIGS. 2 and 3, one embodiment of the present methods and systems for creating connectivity and enabling information exchange between two or more companies is provided. Company A (32), Company 8 (34) and Company C (36) each have data 32A, 34A, 36A (respectively) and software applications 328, 348, 368 (respectively) associated with the function of their business activities. These companies 32, 34, 36 are identified for inclusion in step 52 in a partnership for information exchange between and among the companies 32, 34, 36. Each company 32, 34, 36 in the partnership maintains a connection 32C, 34C, 36C in step 54 to a directory management portal 38 that controls connections 320, 340, 360 and permissions 32E, 34E, 36E defined in step 56 that permit transactions 32F, 34F, 36F or exchanges of information to occur between two or more of the companies 32, 34, 36. Functionality for storing and modifying the connections 320, 340, 360 and the permissions 32E, 34E, 36E resides within one or more transaction directories 40, 42, 44 associated with each company 32, 34, 36 (respectively).

In operation, the directory management portal 38 can include, in one embodiment, a substantially secure web-based gateway to tools that control the content of the transaction directories 40, 42, 44. In another aspect, the content of the transaction directories 40, 42, 44 and the tools provided to a company 32, 34, 36 for establishing and modifying connections 32D, 34D, 36D can reside on the storage systems of an electronic business center (discussed in more detail hereinafter) that performs centralized management functions in effecting exchanges of information in step 58, for example, between and/or among the companies 32, 34, 36.

In one embodiment of the present methods and systems, the directory management portal 38 includes a management security LAN that permits the company 32, 34, 36 to see its connections 32D, 34D, 36D and use templates to modify those connections 32D, 34D, 36D in step 60. For example, the company 32, 34, 36 can readily make a change to its connection to one chemical exchange on the Internet to another chemical exchange without modifying existing software applications 32B, 34B, 36B or implementing new software applications. In another example, the company 32, 34, 36 can disconnect a supplier from its chain of manufacturing by modifying the existing connection to that supplier by accessing the directory management portal 38.

Through use of the transaction directories 40, 42, 44, the companies 32, 34, 36 can use standard transaction templates from a library containing multiple integration standards (e.g., BizTalk, MAPICS, EDI, and the like) to create transaction definitions for exchanging information with a partner company. A company 32, 34, 36 can also control partner access through the permissions layer 32E, 34E, 36E and view partner data connections 32D, 34D, 36D. In step 62, the company 36 can also create and manage a connection to transaction directories 46F for the data 46A and software applications 46B of a company partner 46 that does not have access to the directory management portal 38 for data exchanges (i.e., a “non-subscriber”). In one embodiment, a web portal can be employed that permits the company 36 to view what the non-subscriber partner 46 would have if it were a subscriber. The non-subscriber company 46 cannot modify the web portal interface 38 and the subscriber partner company 36 retains control of transactions 36F, 46F performed through the directory management portal 38. The subscriber partner company 36 can also view a list in its transaction directory 44 of existing subscriber partners and non-subscriber partners.

In one aspect, the transaction directories 40, 42, 44 can include an Internet site with conventional front-ended security and password capabilities and access to a conventional database of information related to data exchange with one or more of the partner companies. Such a database can include, for example, a list of connections 32D, 34D, 36D by company, a list of connections 32D, 34D, 36D by application, a list of connections 32D, 34D, 36D by data transmission standard, and the like. This database and other storage media can reside at a storage location associated with a centralized manager (described hereinafter) for the transaction directories 40, 42, 44. In another aspect, information related to connections 32D, 34D, 36D and transactions between and among companies 32F, 34F, 36F can be listed in a conventional spreadsheet format, for example, for review by one of the companies 32, 34, 36.

A translation engine 48 permits information to be exchanged between two or more of the companies 32, 34, 36. In one embodiment of the present methods and systems, the translation engine 48 can include a centralized transaction manager that handles data transformation, transportation and routing between collaborating companies 32, 34, 36. The translation engine 48 can employ subscriber transaction definitions to effect this translation and transportation of data between and among the partner companies 32, 34, 36. Upon receiving a data request, an electronic commerce center (described hereinafter) and the translation engine 48 use the data descriptions residing in the transaction directories 40, 42, 44 to translate information as it is transmitted and received between and among the companies 32, 34, 36.

It can be appreciated that the present methods and systems permit companies to create peer-to-peer relationships with other partner companies without substantial modification of internal data and applications. Using a secure web portal, companies can manage information about the location and format of their shared data and applications. Due to centralized management of transaction directories, a company's information systems and data remain in an environment internal to the company. It can be seen that the translation and collaboration features of the present methods and systems can reduce or substantially eliminate dependency by a company on core systems when building new applications and working with new partners in a strategic alliance, for example.

For companies that must share information electronically, the present methods and systems provide ease of management, company partner connections are managed and monitored through a single gateway; provide security, a company can route external connections through a single point of firewall penetration; reduce the cost of partner integration, a company's connections may be reused for multiple partners; increase flexibility, a company can easily change or multiply partners as required; provide minimal disruption, a company's information systems typically do not have to conform to any particular standard for data format or data communication to be applied to the present methods and systems.

Referring now to FIG. 4, in another embodiment of the present methods and systems, the above-described centralized management features associated with information exchange between partners can be employed for product design and development. As shown, a number of companies 72, 7 4, 76, 78 access a product design and development application 80 through a web portal 82 that provides a single collaborative point of access and control to features of the application 80 for each company 72, 74, 76, 78. The web portal 82 allows a project team administrator, for example, to perform certain tasks including, for example, establishing security and permission levels for team members, controlling access and delivering customized views based on permission level of team members, and monitoring and reporting on team member activity. In one embodiment, the web portal 82 can include a secure web portal that is hosted by an electronic business center at a centralized location.

In one embodiment, an adaptive planning module 84 allows subscribers to create, optimize and save workflow processes and production implementation plans in a saved processes storage medium 86. The adaptive planning module 84 can permit queries of both private repositories 88 and public repositories 90 to access existing processes in storage 86 and “best practices” information 92 that may be available in one or more of the public repositories 90. The adaptive planning module 84 can also include software modules that link components of product/service design to production/implementation steps to forecast cost and time to produce/implement the product. The adaptive planning module 84 can also have an associated partner research module 94 that executes “what if” scenarios with different components/raw material and/or different partners to assess impact on the design, production/implementation process, cost and timing. The adaptive planning module 84 can also have an associated virtual prototyping module 96 that interacts with the private repositories 88 and public repositories 90 to obtain design information, for example.

In another embodiment of the present methods and systems, the virtual prototyping module 96 allows the companies 72, 74, 76, 78 to substantially concurrently build, test and refine a design virtually using collaborative software and “best-in-class” prototyping tools. The virtual prototyping module 96 can provide access to internal company designs such as, for example, blueprints 98, models 100, parts 102, and products 104 that are specific and possibly proprietary to one of the companies 72, 74, 76, 78. The virtual prototyping module 96 can also provide access and queries of one or more product catalogs 106, for example, in the public repositories 90 to help assess options for outsourcing components of a product, for example.

In another embodiment, the partner research module 94 can access the two types of repositories 88, 90. The private repositories 88 of the subscriber companies 72, 74, 76, 78 can include, for example, company profile information 108, preferred supplier and partner profile information 110, and potential partner information 112. The public repositories 90 to which the companies 72, 74,76, 78 have access can include a company contact directory 114 and a public profile 116 for existing or potential company partners. The partner research module 94 allows subscribers to maintain their company and partner profile information which can include, for example, type of business (e.g., raw material, assembly/packaging, manufacturing, transportation and distribution, warehouse/inventory, and the like); and business practices (e.g., core values, staffing, partnering, business initiative, financials, customer satisfaction, and the like). The partner research module 94 also provides search capabilities for identifying potential partner companies by selecting and prioritizing elements from the company information obtained from the repositories 88, 90. The module 94 also allows interactive analysis to refine partner search results obtained from profile queries.

In connection with the illustration of FIG. 5, the following is an example of the operation of the present methods and systems in connection with product design and development:

I. Design & Planning Phase

-   -   A. The project development team has an idea.     -   B. The team logs in and initializes the workflow process using         the adaptive planning module.     -   C. The team creates a design for the idea in the virtual         prototyping module.     -   D. Concurrently, the team updates the workflow process in the         adaptive planning module. To help minimize upfront planning         time, the team executes queries in their private repository for         saved processes matching current project needs.     -   E. The team continues to refine the design and utilizes the         query function in the virtual prototyping module to scan private         and public product catalogs for models, parts and products to         help assess in-sourcing I outsourcing needs and possibilities.     -   F. Based on the identified needs, the team utilizes the partner         research module to scan a library of preferred supplier/partners         for a possible match. The team can extend the search by         pre-defining a company profile and then executing the query in         the public company profile repository. Results of that query can         be stored in the library of potential suppliers/partners.

II. Simulating the Production Process

-   -   A. The team runs “what if” scenarios in the adaptive planning         module with different components/raw materials and/or different         partners/suppliers to assess impact on design, production         process, cost and time.     -   B. Based on these scenarios, the production process is         optimized, and the supply network is assembled including         identification of appropriate suppliers.

The benefits of the present methods and systems as applied to product design and development are readily apparent. In certain embodiments, the present methods and systems provide an Internet-hosted environment that offers a single point of access and control. This allows subscribing companies to increase the speed of bringing new products and services to market, reduce research and development investment, simulate and integrate collaborative design/prototyping, product planning, and partnering activities.

The following operational examples provide potential embodiments of the methods and systems described herein. Such examples are provided for illustration of the present disclosure and are not intended to limit any particular aspect of the present invention.

The table of FIG. 6 provides a list of industry terms equivalent or related to those applied to the present methods and systems with regard to “CONDOR” and “HALO” technology. It can be appreciated that choice of a particular nomenclature for the present methods and systems is merely for convenience of disclosure and is not intended to limit any particular aspect of the present invention.

The schematic of FIG. 7 shows the various components of a centralized manager 122 and its associated functionality that can be employed to implement various embodiments of the present methods and systems. The centralized manager 122 includes centralized management 124 and a process engine 126 for accessing information and effecting transactions. Also shown are examples of inter-enterprise data/system connectors 128 and examples of registered services 130 for use by partner companies.

FIG. 8 shows the interaction between one or more business centers 142, 144, 146, 148 and a centralized manager 150. FIG. 8 provides an example of the interaction of the centralized manager 150 with a number of the electronic business centers 142, 144, 146, 148 that store and process the data and functionality that enables the exchange of information between partner companies (as discussed hereinabove).

FIGS. 9 through 15 illustrate potential tool sets (and issues associated with the use of the tool sets) for implementing various embodiments of the present methods and systems. FIG. 9 includes a tabulation of potential tool sets that can be used in connection with the directory management portal. FIG. 1 0 includes a tabulation of potential tool sets that can be used in connection with the transaction directories. FIG. 11 includes a tabulation of potential tool sets that can be used in connection with the translation engine. FIG. 12 includes a tabulation of potential tool sets that can be used in connection with the adaptive planning module. FIG. 13 includes a tabulation of potential tool sets that can be used in association with the virtual prototyping module. FIG. 14 includes a tabulation of potential tool sets that can be used in connection with the partner research module. FIG. 15 shows a tabulation of potential combinations of tool sets that can be assembled and implemented to provide one or more operational embodiments of the present methods and systems.

The term “computer-readable-medium” is defined herein as understood by those skilled in the art. A computer-readable medium can include, for example, memory devices such as diskettes, compact discs of both read-only and writeable varieties, optical disk drives, and hard disk drives. A computer-readable medium can also include memory storage that can be physical, virtual, permanent, temporary, semi-permanent and/or semi-temporary. A computer-readable medium can further include one or more data signals transmitted on one or more carrier waves.

As used herein, a “computer” or “computer system” may be a wireless or wireline variety of a microcomputer, minicomputer, laptop, personal data assistant (PDA), cellular phone, pager, processor, or any other computerized device capable of transmitting and receiving data over a shared network. Computer devices disclosed herein can include memory for storing certain software applications used in obtaining, processing and communicating data. It can be appreciated that such memory can be internal or external. The memory can also include any means for storing software, including a hard disk, an optical disk, floppy disk, ROM (read only memory), RAM (random access memory), PROM (programmable ROM), EEPROM (extended erasable PROM), and other like computer-readable media.

It can be appreciated that, in some embodiments of the present methods and systems disclosed herein, a single component can be replaced by multiple components, and multiple components replaced by a single component, to perform a given function. Except where such substitution would not be operative to practice the present methods and systems, such substitution is within the scope of the present invention.

Examples presented herein are intended to illustrate potential implementations of the present method and system embodiments. It can be appreciated that such examples are intended primarily for purposes of illustration. No particular aspect or aspects of the example method and system embodiments described herein are intended to limit the scope of the present invention.

Whereas particular embodiments of the invention have been described herein for the purpose of illustrating the invention and not for the purpose of limiting the same, it can be appreciated by those of ordinary skill in the art that numerous variation of the details; materials and arrangement of parts may be made within the principle and scope of the invention without departing from the invention as described in the appended claims. 

1. A method for exchanging information between collaborative entities, the method comprising: operatively associating, by a directory management portal, a first entity with a transaction directory through the directory management portal, the transaction directory being configured to permit establishment of a first connection between the first entity and a translation engine for permitting a transaction to occur through the first connection; connecting, by the directory management portal, a second entity to the translation engine to permit the transaction to occur between the first entity and the second entity, the transaction including an exchange of information associated with a product design between the first entity and the second entity, wherein the directory management portal permits the first entity to monitor and change the first connection to the translation engine using a transaction template selected from a library to create a transaction definition for exchanging information with the second entity; accessing information associated with the first and second entities and effecting transactions, by the translation engine, via the first connection through the translation engine; permitting, by the directory management portal, the first entity to create a second connection to data associated with a non-subscribing entity, wherein the non-subscribing entity does not have access to the directory management portal; receiving, at the directory management portal, a query for an existing process related to the product design; in response to the query, searching, by the directory management portal, private repositories associated with the first entity and the second entity and public repositories accessible by the first entity and the second entity for the existing process; executing, by the directory management portal, a variety of scenarios with different components and suppliers to determine an impact on the product design; and associating, by the directory management portal, components of the product design with production steps to forecast a cost for producing the product design.
 2. The method of claim 1, further comprising operating the translation engine externally with regard to a software application of the first and second entities.
 3. The method of claim 1, further comprising establishing a permission for the occurrence of the transaction between the first and second entities.
 4. The method of claim 1, further comprising searching the private repositories associated with the first entity and the second entity for models, parts, and products to access outsourcing needs for the product design.
 5. The method of claim 1, wherein the directory management portal includes a web-based gateway.
 6. The method of claim 1, further comprising connecting the first and second entities to an additional partner entity by accessing the transaction directory through the directory management portal.
 7. The method of claim 1, further comprising disconnecting a partner entity from the first and second entities by accessing the transaction directory through the directory management portal.
 8. A method for exchanging information between collaborative entities, the method comprising: operatively associating, by a directory management portal, a first entity with a transaction directory through the directory management portal, the transaction directory being configured to permit establishment of a first connection between the first entity and a translation engine for permitting a transaction to occur through the first connection; connecting, by the directory management portal, a second entity to the translation engine to permit the transaction to occur between the first entity and the second entity, the transaction including an exchange of information associated with a product design between the first entity and the second entity, wherein the directory management portal permits the first entity to monitor and change the first connection to the translation engine using a transaction template selected from a library to create a transaction definition for exchanging information with the second entity; accessing information associated with the first and second entities and effecting transactions, by the translation engine, via the first connection through the translation engine; permitting, by the directory management portal, the first entity to create a second connection to data associated with a non-subscribing entity, wherein the non-subscribing entity does not have access to the directory management portal; receiving, at the directory management portal, a query for an existing process related to the product design; in response to the query, searching, by the directory management portal, private repositories associated with the first entity and the second entity and public repositories accessible by the first entity and the second entity for the existing process; executing, by the directory management portal, a variety of scenarios with different components and suppliers to determine an impact on the product design; and associating, by the directory management portal, components of the product design with production steps to forecast an amount of time to produce the product design.
 9. The method of claim 7, further comprising operating the translation engine externally with regard to a software application of the first and second entities.
 10. The method of claim 7, further comprising establishing a permission for the occurrence of the transaction between the first and second entities.
 11. The method of claim 7, wherein the directory management portal includes a web-based gateway.
 12. The method of claim 7, further comprising connecting the first and second entities to an additional partner entity by accessing the transaction directory through the directory management portal.
 13. The method of claim 7, further comprising disconnecting a partner entity from the first and second entities by accessing the transaction directory through the directory management portal.
 14. The method of claim 7, further comprising searching the private repositories associated with the first entity and the second entity for models, parts, and products to access outsourcing needs for the product design.
 15. A non-transitory computer-readable storage medium having instructions stored thereon that, when executed by a computer, cause the computer to perform a method comprising: operatively associating a first entity with a transaction directory through a directory management portal, the transaction directory being configured to permit establishment of a first connection between the first entity and a translation engine for permitting a transaction to occur through the first connection; connecting a second entity to the translation engine to permit the transaction to occur between the first entity and the second entity, the transaction including an exchange of information associated with a product design between the first entity and the second entity, wherein the directory management portal permits the first entity to monitor and change the first connection to the translation engine using a transaction template selected from a library to create a transaction definition for exchanging information with the second entity; accessing information associated with the first and second entities and effecting transactions via the first connection through the translation engine; permitting the first entity to create a second connection to data associated with a non-subscribing entity, wherein the non-subscribing entity does not have access to the directory management portal; receiving a query for an existing process related to the product design; in response to the query, searching private repositories associated with the first entity and the second entity and public repositories accessible by the first entity and the second entity for the existing process; executing a variety of scenarios with different components and suppliers to determine an impact on the product design; and associating components of the product design with production steps to forecast a cost for producing the product design.
 16. The non-transitory computer-readable storage medium of claim 15, having further instructions stored thereon that, when executed by the computer, cause the computer to perform a method comprising operating the translation engine externally with regard to a software application of the first and second entities.
 17. The non-transitory computer-readable storage medium of claim 15, having further instructions stored thereon that, when executed by the computer, cause the computer to perform a method comprising establishing a permission for the occurrence of the transaction between the first and second entities.
 18. The non-transitory computer-readable storage medium of claim 15, having further instructions stored thereon that, when executed by the computer, causes the computer to perform a method comprising connecting the first entity and the second entity to an additional partner entity by accessing the transaction directory through the directory management portal.
 19. The non-transitory computer-readable storage medium of claim 15, having further instructions stored thereon that, when executed by the computer, causes the computer to perform a method comprising disconnecting the first entity and the second entity from a partner entity by accessing the transaction directory through the directory management portal.
 20. The non-transitory computer-readable storage medium of claim 15, having further instructions stored thereon that, when executed by the computer, causes the computer to perform a method comprising associating the components of the product design with the production steps to forecast an amount of time for producing the product design. 